feat(frontend): add accessibility statement page - #122

@shoaib050326 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Someone is attempting to deploy a commit to the smartdevs17's projects Team on Vercel.

A member of the Team first needs to authorize it.

I checked the latest CI run for this PR after rebasing onto the current upstream main, and the PR is still failing due to unrelated repository issues rather than the accessibility statement changes in this branch.

Latest run:

• 23510761450

Current failing checks:

• Backend (Node.js 22)
• Frontend (Node.js 20)
• Smart Contracts (Rust)

Exact errors from the latest run:

• Frontend build: frontend/app/dashboard/projects/[id]/page.tsx:208
  • Type error: 'verification' is of type 'unknown'
• Backend lint: backend/src/services/catalog.ts:11
  • ESLint error: 'e' is defined but never used
• Contracts build: contracts/src/lib.rs:143
  • Rust build error: missing field deadline in Project initializer

The changes in this PR are limited to:

• frontend/app/accessibility/page.tsx
• frontend/app/page.tsx

So the current red CI appears to be caused by existing failures in unrelated frontend, backend, and contract files, not by the accessibility page implementation in this PR.

Hi @Smartdevs17 I’m happy to help unblock CI if useful. Would you prefer that I open a separate PR to fix the unrelated failing checks, so this accessibility PR can stay focused on issue #99?